no-unsafe-catch-error-property (and its promise variant) only flagged .message, .stack, .code on unguarded caught error variables — missing .status accesses like if (err.status === 404) that are common in HTTP error handling.

Changes

• Broadened UNSAFE_PROPERTIES in both no-unsafe-catch-error-property and no-unsafe-promise-catch-error-property to include status, cause, and name
• Added typeof err === 'object' as an accepted guard (strict === only; alongside existing instanceof Error and getErrorMessage guards) — real call sites that check typeof err === 'object' before reading .status are no longer false positives
• New RuleTester cases for all three new properties (invalid without guard) and typeof guard variants (valid)

// Now flagged:
try { ... } catch (err) { if (err.status === 404) { } }
//                              ^^^^^^^^^^

// Still suppressed — typeof guard recognized:
try { ... } catch (err) { if (typeof err === 'object') { doSomething(err.status); } }